home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19970326-19970626
/
000056_news@columbia.edu _Sat Apr 5 12:25:06 1997.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
2KB
Return-Path: <news@columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id MAA12930
for <kermit.misc@watsun.cc.columbia.edu>; Sat, 5 Apr 1997 12:25:06 -0500 (EST)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id MAA17005
for kermit.misc@watsun; Sat, 5 Apr 1997 12:25:03 -0500 (EST)
Path: news.columbia.edu!watsun.cc.columbia.edu!fdc
From: fdc@watsun.cc.columbia.edu (Frank da Cruz)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: K95 Script Local Echoing
Date: 5 Apr 1997 17:24:56 GMT
Organization: Columbia University
Lines: 27
Message-ID: <5i61t8$59$1@apakabar.cc.columbia.edu>
References: <Pine.SUN.3.94.970405105100.9562A-100000@mercury>
NNTP-Posting-Host: watsun.cc.columbia.edu
Xref: news.columbia.edu comp.protocols.kermit.misc:6871
In article <Pine.SUN.3.94.970405105100.9562A-100000@mercury>,
Jay Daly <jay@bidmc.harvard.edu> wrote:
:
: When running script-managed telnet sessions with K95 (1.1.11), characters
: sent via the output command aren't echoed locally. Characters typed in
: CONNECT mode are, though, as are characters sent via the TRANSMIT command
: (which follows the local SET TERM setting, according to Using C-K e2;
: again indicating that the local echo is set appropriately). A check of
: the active connection shows that "Echoing is currently local."
:
: I don't want to have them echoed by the remote server, since everything
: works fine in connect mode, and I can manually insert echo commands into
: the script to display such output data as might be necessary to clarify
: the session, but I thought I'd check first to see if I was missing
: something.
:
: Maybe some magical SET OUTPUT ECHO ON command?
:
: TIA for any help you can give. (BTW, no problem with echoing output in
: similar scripts using MSK 3.15.)
:
Good call. If DUPLEX is HALF (or TERMINAL ECHO is LOCAL, same thing) and
SET INPUT ECHO is ON, then OUTPUT should also echo locally. Presently it
does not. We'll fix this in the next release. (Btw, OUTPUT does handle
session logging correctly in this case.)
- Frank